Skip to main content

firelabs migration

📘 Firelabs migration​

  • 🚀 Create the release v1.0.0 🛫 2024-02-26 📅 2024-03-03 ✅ 2024-02-22
    • landing 📅 2024-02-21 ✅ 2024-02-22
    • public 📅 2024-02-22 ✅ 2024-02-22
    • logs 📅 2024-02-23 ✅ 2024-02-22
    • server 📅 2024-02-24 ✅ 2024-02-22
    • client 📅 2024-02-25 ✅ 2024-02-22
  • 🚀📖 landing, docs, logs migration (forking and create a new repository "Firelabs") ✅ 2024-02-25
  • 🚀😎 web client (+tests +deployments) #priority 📅 2024-02-29 ✅ 2024-02-25
    • 🔨 Before the deployment of this release/1.0.0 I will have to deploy the firebase functions and save in Firestore the initial data for the events that must be read so it starts with all the previous data instead of having to do all the reading in the executions, that might take several days to get up to today. ✅ 2024-02-25
  • Is this really needed? No . . . I have all teh code already deployed
    • 🚀📃 smart contracts (+tests +deployments) #priority
      • Adding "cannon" or deployments with "Foundry" to the smart contract pipeline here with hardhat and Foundry
      • Upgradable contracts with Foundry here
    • 🚀💻 server code (+tests +deployments) #priority
      • 🔧 Improve the execution of actions in the blockchain (right now many times fail or simply do not know if executed successfully). Recommendation from Jabato using free layer from Amazon

📖 Scenarios:​

✍ (0) Use "cannon" for smart contract migration/deployment​

🌍 cannon guide here 🌍 Make a video of Firelabs so I can put it as "portfolio"

✍ (1) Making deposit available​

Given I am the User When I click on the deposit button Then I do a staking in Firelabs that will daily compound in the 5% staking of Nimbus Platform

  1. Step 1 . . .
  2. Step 2 . . .
  3. Step 3 . . .

✍ (2) Making withdrawal available​

Given I am the User When I click on the withdrawal button Then I receive my rewards plus all the staking body I sent to Firelabs in the 5% staking of Nimbus Platform